Live streaming video sharing system and related methods

ABSTRACT

A live streaming video sharing system. Implementations may include a video camera, portable computing device, video streaming server, database, application server, web server, and a portable computing device associated with a user operatively coupled together. The video camera sends a live stream of video data wirelessly to the portable computing device. The computing device associated with a user receives a live stream of video data from the web server, processes the live stream of video data, and generates a computer interface. The computer interface may include a public computer interface including a public channel and an invisible computer interface including an invisible shares channel associated with the user including an icon corresponding with one or more invisible shares, each invisible share corresponding with a live stream of video data and each invisible share not retrievable using a search form in the computer interface, the application server, and the database.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of the earlier U.S.Utility Patent Application to Lee Bliss, et al., entitled “LiveStreaming Video Sharing System And Related Methods,” application Ser.No. 14/675,478, filed Mar. 31, 2015, now pending, which was acontinuation application of the earlier U.S. Utility Patent Applicationto Lee Bliss, et al., entitled “Live Streaming Video Sharing System AndRelated Methods,” application Ser. No. 14/150,583, filed Jan. 8, 2014,now U.S. Pat. No. 8,997,167, issued Mar. 31, 2015, the disclosures ofwhich are hereby incorporated entirely herein by reference.

BACKGROUND 1. Technical Field

Aspects of this document relate generally to systems and methods usedfor streaming video across a telecommunications network to computingdevices.

2. Background Art

Conventional video capture devices such as camcorders capture video byconstructing a series of video frames and capturing surrounding audiousing a microphone. Various data formats for storing the video and audioinformation and synchronizing the video and audio have been developed.Conventional video capture devices are directed to the capturing andstorage of video and audio for playback at a later time to a particularviewer.

SUMMARY

Implementations of live streaming video sharing systems may include avideo camera, a portable computing device operatively coupled with thevideo camera through a wireless telecommunication channel, and a videostreaming server operatively coupled with the portable computing devicethrough a wireless telecommunication channel. The system may alsoinclude a database operatively coupled with the video streaming serverand a web server. The video camera may be adapted to send a live streamof video data using a first data transmission protocol across thewireless telecommunication channel to the portable computing device. Theportable computing device may be adapted to receive the live stream ofvideo data in the first data transmission protocol, process the livestream of video data, and send the live stream of video data across thewireless telecommunication channel using a second data transmissionprotocol to the video streaming server. The video streaming server maybe adapted to receive the live stream of video data, process the livestream of video data in the second data transmission protocol, and sendthe live stream of video data using a third data transmission protocolinto a telecommunication channel. The system may also include acomputing device associated with a user where the computing device isadapted to receive the live stream of video data, process the livestream of video data in the third data transmission protocol, andgenerate a computer interface in response to receiving the live streamof video data. The computer interface may include a public computerinterface including one or more public channels including one or moreicons corresponding with one or more public shares where each publicshare corresponds with a live stream of video data. The public computerinterface may also include a search form adapted to permit a user tosearch all public shares in the system using the application server andthe database to retrieve a list of all public shares associated with asearch term entered into the search form where each public sharecorresponds with a live stream of video data. The computer interface mayalso include an invisible computer interface including an invisibleshares channel associated with the user where the invisible shareschannel includes one or more icons corresponding with one or moreinvisible shares, each invisible share corresponding with a live streamof video data and each invisible share not retrievable using the searchform, the application server, and the database. The invisible computerinterface may further include an invisible shares inbox associated withthe user which includes one or more icons corresponding with one or moreinvisible shares received by the user from another user of the system.One of the icons in the public computer interface or the invisiblecomputer interface is associated with the live stream of video data andmay be adapted, when selected by the user, to generate a viewingcomputer interface that includes the live video stream from the videocamera.

Implementations of live streaming video sharing systems may include one,all, or any of the following:

The video camera may be a point-of-view (POV) video camera and the livestream of video data may be a live stream of POV video data.

The computer interface may further include a private computer interfaceincluding one or more private channels including one or more iconscorresponding with one or more private shares associated with the userwhere the association of each of the one or more private shares isestablished through the database and an account associated with theuser.

The system may further include a sharebox interface which may includeone or more public and/or one or more private shares sent to the user byone or more other users of the system using the application server andthe database. Each of the one or more public and/or the one more privateshares may be adjacent to an icon representing an identity of the one ormore other users of the system.

The computer interface may further include a tap button adjacent to achannel where the tap button is configured to permit a user to store anindication in the database that configures the application server tosend a notification to the user when a new share for the channeladjacent to the tap button is available.

The invisible computer interface may include a share fault and a receivevalue associated with the user, each of the share vault and the receivevault being configured to receive an address associated with anotheruser of the system and permit the user to receive invisible shares fromthe user associated with the address.

Implementations of live streaming video sharing systems may utilizeimplementations of a method of generating and transmitting livestreaming POV video. The method may include encoding live POV video datausing a POV video camera and streaming the live POV video into awireless telecommunication channel to a portable computing deviceoperatively wirelessly coupled with the video camera where the live POVvideo is transmitted using a first data transmission protocol. Themethod may also include streaming the live POV video data into awireless telecommunication channel to a video streaming serveroperatively coupled with the portable computing device through awireless telecommunication channel where the live POV video data istransmitted using a second data transmission protocol. In response toreceiving the live POV video data, the method may include recording oneor more channel characteristics associated with the live POV video andincluded in the live POV video data in a database operatively coupledwith the video streaming server and an applications server using thevideo streaming server or the application server. The method may alsoinclude streaming the live POV video data into a telecommunicationchannel to a computing device associated with a user using one of thevideo streaming server, the application server, and a web server wherethe live POV video data is transmitted using a third data transmissionprotocol. The method may include processing the live POV video data andgenerating a computer interface using the computing device and the oneor more channel characteristics. The computer interface may include, ifthe one or more channel characteristics indicate the live POV video datais associated with a public channel, a public computer interface. Thecomputer interface may include, if the one or more channelcharacteristics indicated that the live POV video data is associatedwith an invisible channel associated with the user, an invisiblecomputer interface. One of the icons in the public computer interface orthe invisible computer interface is associated with the live POV videodata. In response to selection of an icon associated with the live POVvideo data, the method may include playing live POV video using the livePOV video data in a viewing computer interface using the computingdevice.

Implementations of a method of generating and transmitting livestreaming POV video may include one, all, or any of the foregoing:

The method may include caching the live POV video data on theapplication server to form a share and providing access to another userof the system to the share on the application server using the databaseand the application server by generating an icon in one of the publiccomputer interface, a private computer interface, or the invisiblecomputer interface corresponding with the share if the share is publicshare, private share, or invisible share, respectively.

The method may also include storing an entire quantity of live POV videodata associated with the share on the application server and providingaccess to another user of the system to the share on the applicationserver using the database and the application server by generating anicon in the private computer interface or the invisible computerinterface corresponding with the share if the share is a private shareor invisible share, respectively.

The method may further include sharing the live POV video data withanother user of the system by caching the live POV video data or storingan entire quantity of live POV video data using the application serveror the video streaming server to create a share. In response toselecting of an address associated with the other user, the method mayinclude creating an icon in a sharebox computer interface associatedwith the other user using the database and the application server and acomputing device associated with the other user.

The method may further include sharing the live POV video data from theuser with a receiving user of the system by caching the live POV videodata or storing an entire quantity of live POV video data using theapplication server or the video streaming server to create an invisibleshare. The method may further include n response to entry of an addressassociated with the receiving user in a share vault associated with theuser included in the invisible computer interface and entry of anaddress associated with the user of the system into a receive vaultassociated with the receiving user included in an invisible computerinterface on a computing device associated with the receiving user. Themethod may then include creating an icon in an invisible channelincluded in the invisible computer interface associated with thereceiving user using the database and the application server.

The method may further include activating the POV video camera to entera channel selection mode, audibly speaking one or more names of one ormore channels associated with the user from the POV video camera usingan earpiece coupled to the POV video camera, receiving a selection of achannel, audibly speaking the name associated with the selected channel,and activating the POV video camera to enter a recording mode.

The method may further include determining a location of the POV videocamera using a global positioning system (GPS) signal received by thePOV video camera and a location services system accessed wirelessly bythe POV video camera through the portable computing device associatedwith the user and assigning one or more contextual geographical searchterms to the channel selected using the location and the POV videocamera. The method may also include including one of the location andthe one or more contextual geographical search terms in the one or morechannel characteristics.

The method may further include where recording one or more channelcharacteristics associated with the live POV video and included in thelive POV video data further includes where the one or more channelcharacteristics are a location of the POV video camera, one or morecontextual geographic search terms, an address associated with a user, achannel name, a channel type, or any combination thereof.

Implementations of live streaming video sharing systems may utilizeimplementations of a method of transmitting live streaming video to apublic channel and to an invisible channel. The method may includereceiving live video data using a streaming server from a wirelesstelecommunication channel where the live video data is transmitted usinga second data transmission protocol and a portable computing device. Theportable computing device receives the live video data from a wirelesstelecommunication channel using a first data transmission protocol froma video camera. In response to receiving the live video data, the methodmay include recording one or more channel characteristics associatedwith the live video included in the live video data in a databaseoperatively coupled with the video streaming server and an applicationserver using the application server or the video streaming server. Themethod may further include providing access to the live video data usingthe database and the one or more channel characteristics through atelecommunication channel using the video streaming server, theapplication server, or a web server where the video streaming server,the application server, or the web server are adapted to, in response toa request from a computing device associated with a user, stream thelive video data using the telecommunication channel and a third datatransmission protocol to the computing device. The computing device maybe adapted to generate a computer interface using the computing deviceand the one or more channel characteristics. The computer interface mayinclude, if the one or more channel characteristics indicate the livevideo data is associated with a public channel, a public computerinterface. The computer interface may, if the one or more channelcharacteristics indicated the live video data is associated with aninvisible channel associated with the user, a private computerinterface. One of the icons in the public computer interface or in theprivate computer interface is associated with the live video data. Inresponse to selection of an icon associated with the live video data inthe public computer interface or in the private computer interface, thecomputing device may be adapted to play live video using the live videodata in a viewing computer interface.

Implementations of a method of transmitting live streaming video to apublic channel and to an invisible channel may include one, all, or anyof the following:

The method may include sharing the live video data with another user ofthe system by caching the live video or storing an entire quantity oflive video data using the application server or the video streamingserver to create a share and in response to a selection of an addressassociated with the other user, creating an icon in a sharebox computerinterface associated with the other user using the database and theapplication server and a computing device associated with the otheruser.

The method may further include sharing the live video data from the userwith a receiving user of the system by caching the live video data orstoring an entire quantity of live POV video data using the applicationserver or the video streaming server to create an invisible share. Themethod may further include, in response to entry of an addressassociated with the receiving user in a share vault associated with theuser included in the invisible computer interface and entry of anaddress associated with the user of the system into a receive vaultassociated with the receiving user included in an invisible computerinterface on a computing device associated with the receiving user,creating an icon in an invisible channel included in the invisiblecomputer interface associated with the receiving user using the databaseand the application server.

The method may further include activating the video camera to enter achannel selection mode, audibly speaking one or more names of one ormore channels associated with the user from the video camera using anearpiece coupled to the video camera, receiving a selection of achannel, audibly speaking the name associated with the selected channel,and activating the video camera to enter a recording mode.

The method may include determining a location of the video camera usinga GPS signal received by the video camera and a location services systemaccessed wireless by the video camera through the portable computingdevice associated with the user, and assigning one or more contextualgeographical search terms to the channel selected using the location andthe video camera. The method may also include including one of thelocation and the one or more contextual geographical search terms in theone or more channel characteristics.

Recording one or more channel characteristics associated with the livevideo and included in the live video may include wherein the one or morechannel characteristics are a location of the video camera, one or morecontextual geographic search terms, an address associated with a user, achannel name, a channel type, or any combination thereof.

The foregoing and other aspects, features, and advantages will beapparent to those artisans of ordinary skill in the art from theDESCRIPTION and DRAWINGS, and from the CLAIMS.

BRIEF DESCRIPTION OF THE DRAWINGS

Implementations will hereinafter be described in conjunction with theappended drawings, where like designations denote like elements, and:

FIG. 1 is a block diagram of an implementation of a live streaming videosharing system;

FIG. 2 is a view of an implementation of a home screen computerinterface;

FIG. 3 is a view of an implementation of a me-shares computer interface;

FIG. 4 is a view of an implementation of a everybody-shares computerinterface;

FIG. 5 is a view of an implementation of a sharebox interface;

FIG. 6 is a view of the implementation of sharebox interface of FIG. 5with one of the icons selected;

FIG. 7 is a view of an implementation of an invisible shares computerinterface or an invisible computer interface;

FIG. 8 is a view of an implementation of a public computer interface;

FIG. 9 is a view of an implementation of a computer interface or viewinginterface;

FIG. 10 is a view of a search results computer interface;

FIG. 11 is a view of a channel properties interface;

FIG. 12 is a database structure diagram of a database implementation;

FIG. 13 is a flowchart of an implementation of a method of generatingand transmitting live POV video.

DESCRIPTION

This disclosure, its aspects and implementations, are not limited to thespecific components, assembly procedures or method elements disclosedherein. Many additional components, assembly procedures and/or methodelements known in the art consistent with the intended live streamingvideo sharing system will become apparent for use with particularimplementations from this disclosure. Accordingly, for example, althoughparticular implementations are disclosed, such implementations andimplementing components may comprise any shape, size, style, type,model, version, measurement, concentration, material, quantity, methodelement, step, and/or the like as is known in the art for such livestreaming video sharing system, and implementing components and methods,consistent with the intended operation and methods.

Referring to FIG. 1, an implementation of a live streaming video sharingsystem 2 is illustrated. As illustrated, the system 2 includes a videocamera 4 that is coupled wirelessly to a portable computing device 6.Due to the wireless nature of the connection, the video camera 4 isphysically separate from the portable computing device 6. In variousimplementations of the system the video camera 4 is a capshall. As usedherein, the term “capshall” is a term that refers to a video cameradevice that engages with a human ear (and may be oriented over the humanear) which contains an audio input/output component. A capshall containsa video component that is pointed outwardly away from a user in the sameperspective as the user's eye and may be approximately located at eyelevel. The audio component of the capshall is positioned to be close tothe auditory canal to permit the user to hear the output from thecapshall in privacy, similar to a headphone design. In addition, theaudio component of the capshall includes a microphone that is directedto capture sounds coming from the same direction that the video beingtaken by the device is coming as well as speech commands from the user.

In various implementations, the audio component of the capshall may takethe form of an earpiece coupled to the video component. The capshallpermits the user to be able to take point-of-view (POV) video.Point-of-view video refers to a perspective that is substantially thesame as what the user sees with their eyes in a particular place orsituation and which continuously moves with any change in the user'sposition to show what the user can see. Since the capshall is worn bythe user on their head and the video component may be positioned neareye level, the capshall permits the capture of live POV video (includingaudio) from the user's point of view and perspective. The capshall mayalso include other user interface components, such as one or morebuttons to enable user selection of various options that are audiblyspoken by the audio component.

Implementations of the video camera 4 may continuously capture videoand, therefore, act as a source of live video. In those implementationswhere the video camera 4 generates a stream of live video, the videocamera 4 may process the POV video into POV video data using eitherhardware or software encoding techniques. The video camera 4 may thensend the POV video data to the portable computing device 6 bytransmitting (streaming) the live POV video data into a wirelesstelecommunication channel using a first data transmission protocol. Thenature of the data transmission protocol used may vary. In particularimplementations, the first data transmission protocol is the protocolmarketed under the tradename BLUETOOTH by the Bluetooth Special InterestGroup, Inc. of Kirkland, Wash. In implementations employing BLUETOOTH,the video and audio data included in the live POV video data aretransmitted across the channel using the Audio/Video DistributionTransport Protocol (AVDTP). The AVDTP works to handle the signalinganother coordination of the video and audio streams and interacts withlower level protocols in the BLUETOOTH protocol stack such as LinkManager Protocol (LMP), Logical Link Control Adaptation Protocol(L2CAP), Service Discovery Protocol (SDP), SIM Access Protocol (SAP),and Host Controller Interface (HCl) to ensure that the video and audiostreams are and remain synchronized as they are transmitted from thevideo camera 4 and received and processed by the portable computingdevice 6.

In various implementations, AVDTP is used to control the signalingcommunication between the video camera 4 and the portable computingdevice 6 to ensure that the live POV video (and audio) stream beingreceived remain synchronized. Various algorithms to accomplish this maybe employed in various implementations. In particular implementations,buffering may be employed by the video camera 4, portable computingdevice 6, or both in a “slowest horse” approach. In this technique, ifthe audio stream is determined to be being transmitted more slowly, thenthe video stream speed is reduced to match the audio stream pace. If thevideo stream speed is determined to be slower, then the audio streamtransmission rate is reduced to match the video stream transmissionrate. In particular implementations, a buffer of 1-10 seconds isemployed to enable the algorithm to work to keep the audio and videosynchronized as they are being transmitted from the video camera 4and/or being received and processed by the portable computing device 6.

In various implementations, the use of various video resolutions is alsoemployed as an aid in assisting in keeping the audio and video streamssynchronized in recording time. For example, the video resolution may beabout 200 pixels by 200 pixels, about 300 pixels by 300 pixels, 500pixels by 500 pixels or any other desired resolution or combination ofpixel resolutions (i.e., 500 pixels by 300 pixels) that assists withensuring the live stream can be transmitted successful with the audiostream. In various implementations of the system 2, this means that theultimate viewing size of the video stream matches the video resolutioncaptured and/or transmitted by the video camera 4. Because theresolution of the live POV video data being transmitted may be lowerthan resolutions such as high definition (1920×1080 or 1440×1080) thequantity of video data may be significantly reduced, permitting higherreliability in transmission of the video data over telecommunicationchannels of varying or limited bandwidth capability, which is often thecase in wireless telecommunications. The lower resolution may alsoensure better control of the video and audio streams to ensure theymaintain synchronization.

The portable computing device 6 may be any of a wide variety ofcomputing devices 6. These include, by non-limiting examples, cellphones, smart phones, tablets, laptop computers, wearable computingdevices, e-readers, and any other computing device that can be carriedby a user. Various functions performed by the portable computing device6 may be carried out by software operated by the portable computingdevice 6, which may take the form of an “app” that a user installs onthe portable computing device 6 and downloads from a repositoryassociated with the system 2. The portable computing device 6 contains afirst wireless communication portion that is complementary to thewireless communication portion contained in the video camera 4, andwhich may, in various implementations, may be that marketed under thetradename BLUETOOTH.

The portable computing device 6 receives the live stream of POV videodata and processes it. During processing, AVDTP may be used by theportable computing device 6 to engage in and implement the signaling toenable the algorithms designed to ensure that the video data stream andaudio data stream are kept synchronized. The portable computing device 6also has a second wireless communication portion which is used tocommunicate across a wireless telecommunication channel using a seconddata transmission protocol. In various implementations, the second datatransmission protocol may be any technique or protocol categorized underthe 3G mobile telecommunication standard, such as the InternationalMobile Telecommunications-2000 (IMT-2000) specification. In otherimplementations, the second data transmission protocol may be anytechnique or protocol categorized under the 4G mobile telecommunicationstandard, such as the International Mobile Telecommunications Advanced(IMT-Advanced) specification.

The wireless telecommunication channel may include many intermediatewireless and wired networking components in various implementations,depending upon how the 3G or 4G network is designed. For example, thechannel may include a tower, which wirelessly receives the signal fromthe portable computing device 6 and then transfers the live stream ofvideo (and audio) data to a wired network for further transmission.Because at least a portion of the route to the portable computing device6 involves a wireless transmission, this network configuration is awireless telecommunication channel. The live stream of POV video isreceived by video streaming server 8 in a variety of possibleconfigurations. In the implementation illustrated in FIG. 1, the videostreaming server 8 is coupled to the portable computing device 6 throughan application server 10, which serves to initially receive the live POVvideo stream and any channel characteristics included in the live POVvideo stream and write relevant information to database 12 coupled tothe application server 10. In other implementations, however, the videostreaming server 8 may be directly coupled to the portable computingdevice 6 and send information, including channel characteristics to theapplication server 10 and/or the database 12. A wide variety of networkconfigurations are possible using the principles in this disclosure.

Video streaming server 8 receives the live POV video (and audio) streamand processes (caches) it. In particular implementations, the videostreaming server 8 downloads the live POV video stream in the form of anFLASH video file (.flv file) being created and stored on the portablecomputing device 6. The video streaming server 8 then uses variousmethods and software marketed under the tradename VLC by the VideoLanOrganization of Paris, France to convert the format of video stream datato a format that is streamable, such as, by non-limiting example, asession description protocol (.sdp) formatted file. The video streamingserver 8 then uses the various methods and software marketed under thetradename DARWIN STREAMING SERVER (DSS) by Apple, Inc. of Cupertino,Calif. to make the live POV video data stream available for broadcastingusing the Real-Time Streaming Protocol (RTSP). This technique treats theportable computing device 6 as a web server with a web address on whichthe .fly file can be accessed and downloaded across the wirelesstelecommunication network by the video streaming server 8. Once the datahas been downloaded as a local file, the video streaming server 8 usesVLC to reformat the data to an .sdp file which DSS is used by the videostreaming server 8 to broadcast over a telecommunication channel.

Other techniques may also be employed by the video streaming server 8 toreceive the live POV video stream and broadcast it across thetelecommunication channel, depending on the characteristics and softwarethat exist on the portable computing device 6. For example, where theoperating system run on the portable computing device 6 is that marketedunder the tradename ANDROID by Google, Inc. of Mountain View, Calif.,the methods implemented in the MediaRecorder class may be used by theportable computing device 6 to write a byte stream of data containingthe live POV video data to the video streaming server 8 to create a 3GPP(0.3gp) multimedia file for broadcasting using DSS. In otherimplementations, the methods included in the software marketed under thetradename SIPDROID by Google may be employed to transfer the live POVvideo data from the portable computing device 6 to the video streamingserver 8 for broadcasting with DSS. In other implementations, theReal-time Transport Protocol (RTP) may be used as implemented by ANDROID4.0 ICE CREAM SANDWICH operating system version and other operatingsystems used by the portable computing device 6 to stream live POV videodata to the video streaming server 8.

The live POV video data is made available by the video streaming server8 to other users of the system 2 in several system configurations. Asillustrated in FIG. 1, the video streaming server 8 may process the livePOV video data and send the live stream of video data using a third datatransmission protocol into a telecommunications channel directly to aportable computing device 14 associated with another user or a computingdevice 16 associated with another user of the system. The third datatransmission protocol may include any wired or wireless datatransmission protocol, such as, by non-limiting example, Ethernet, 3G,4G, BLUETOOTH or any other presently existing or future protocol. Thetelecommunications channel used may include any number of wired and/orwireless networking components that couple the portable computing device14 and computing device 16 with the video streaming server 8. In anothersystem configuration, the portable computing device 14 and computingdevice 16 may receive the live stream of POV video data from a webserver 18 which controls access to the data stream by the users throughinteracting with the application server 10 and the database 12. In thiscase, the web server 18 forwards and/or processes the live stream of POVvideo data from the video streaming server 8 to the portable computingdevice 14 and the computing device 16.

The portable computing device 14 may be any previously disclosed in thisdocument. The computing device 16 may be a portable computing devicetype but also may be a desktop computer, server, workstation, or othercomputing system not configured to be physically carried by a user.Furthermore, the various servers discussed in this document may operateon physically separate hardware or may be virtualized and operating onone or more shared physical hardware servers.

The portable computing device 14 and the computing device 16 receive thelive POV video stream and process it, generating various computerinterfaces that permit the user of the system 2 or prospective user ofthe system 2 associated with the portable computing device 14 or thecomputing device 16 to view the POV video. The particular computerinterface constructed depends on the relationship the user streaming thelive POV video (streaming user) has with the user attempting the viewthe POV video (viewing user) and the relationship the viewing user haswith the system 2 (i.e., does the viewing user have an account with thesystem 2 or not?). What the computer interfaces enable the viewing userto do is view the live POV video (or saved POV video in particularsituations) in the form of a “share” or “saved share.” A “share,” asused herein, is defined as a live POV streaming video clip that may beaccessed and displayed to a viewing user through a computer interface.The term “saved share,” as used herein, is defined as a live POVstreaming video clip, or share, that has been saved by a streaming useron the system 2, whether on the database 12, video streaming server 8,web server 8, or other video and audio storage device associated withthe system 2.

Referring to FIG. 8, an implementation of a public computer interface 20is illustrated. As illustrated, the interface 20 includes a publicchannel 22 that shows a plurality of public shares each represented byicons 24, 26, 28. The term “share channel” or “channel,” as used herein,is a website organizational structure used to identify and categorizeshares based on their content and/or access by other users of thesystem. A user of the system may be provided with any suitable number ofchannels for organizing and streaming different types of shares, such asone, two, three, four, five or more, ten or more, twenty of more and anyother number. A channel may be public, private or invisible, dependingupon the access the streaming user provides to the one or more sharesassociated with that particular channel. The association of a particularshare with a particular channel is made by the streaming user using theapplication server 10 and database 12 at the time of recording of theshare or afterward, in the case of a saved share. The public interface20 includes a search form 30 that permits the viewing user to search allof the public channels and public shares in the system at a given time.As illustrated, searches by channels that currently have live POV videocontent can be included and searches by all channels, including thosethat do not currently have live POV video content is enabled throughrespective search buttons.

The term “public share,” as used herein, is defined as a share that isbeen made accessible to any user by the streaming user and may bediscovered through a search. The term “private share,” as used herein,is defined as a share that is only viewable by users that have beenauthorized to view it by the streaming user but may be discoveredthrough a search by all other users of the system. For example, aprivate channel may appear in the search results by all users, butshares streamed through the private channel may not be viewed unlessaccess is provided by the streaming user. An invisible channel cannot beidentified through a search and access is limited to those users thathave been provided access. A channel may be searched by a user's ID. Achannel may have an associated geographical search term that is relatedto the user's location or the location where the share was recorded.

As illustrated in in FIG. 8, one of the icons in the public channel 22has been selected, which provides a larger view of the icon inpreparation for the viewing user to begin to watch the share. Asillustrated, the title of the public channel 22 is “Most Popular Shares”and, accordingly, the public shares included in the public channel couldbe, for example, those that are currently being viewed by the most usersof the system. In various implementations of the system, the viewers ofpublic shares may include those who have not established a user accountwith the system; in others, to view the shares, the prospective viewersmay be required to establish a user account.

Referring to FIG. 2, an exemplary home screen 32 having a number ofchannels with associated share icons is illustrated. A most popularchannel 34 includes icons 36, 38 for the most popular live sharescurrently being streamed by the system 2. In particular implementations,the icons 36, 38 may show the actual video in a reduced thumbnail size,an icon type corresponding to the subject matter of the share, thecontent of the share, or any other desired image type. The scroll icon40 shown on either side of the most popular display, allows a user toscroll the channel window to see other most popular shares. A subscribedchannels channel 42 shows icons for any currently live shares fromchannels within the system that the user has currently subscribed to,which could include channels associated with other system users and paidsubscription channels. To subscribe to a channel, the user must havefirst been provided access to the streaming user's channel, and/or oneor more shares included in that channel. Once subscribed, the shares inthe streaming user's channel are then sent to the viewing user's sharebox interface (to be discussed later) for viewing either live or saved.

A favorites channel 44 shows icons representing any live shares fromchannels that the user has tagged as favorites using the system whichmay be public or private shares from public or private channels. Anysuitable display technique may be used to indicate that a live share isbeing streamed to a channel. For example, the icon for a particularshare may flash, grow in size as it goes live, or have a border thatchanges color or flashes.

Also shown in FIG. 2 is a me-shares channel 46 shows shares from theuser's channels. As illustrated at the upper right of the interface 32,the particular user logged into the system 2 is identified by an icon,username, or other avatar associated with the user along with a dropdown menu that lists various account options when the user is logged in(Dr. Who Options). In various implementations, the user may label thechannel with another title and provide a user defined icon for thechannel.

FIG. 3 illustrates an implementation of a me-shares interface 48(private computer interface) illustrating a plurality of channels 50, 52that form a me-shares library. A user may organize, view, delete andshare shares that the user has or will be recording within the me-shareslibrary. As these shares are created by the user, they are privateshares unless the user decides to make them public using the system 2 orgive other users access to view them. As shown in FIG. 3, a portion ofthe user's channels are shown as horizontal containers having five iconsvisible per channel. As was previously mentioned, various scroll icons54, 56 may be used to move to different channels and to different shareswithin channels. In the me-shares interface 48, the various shares thatare displayed may be both saved shares as well as live shares. In theother interface types, such as the public interface 20 and the homescreen 32, only live POV video shares may be visible in the channels.All shares associated with a particular user that are saved shares maybe visible in this me-shares interface 48. When a user decides to deletea particular saved share, it is permanently removed from the system.

FIG. 4 illustrates an implementation of an everybody-shares interface 58that illustrates various shares from other users of the system. Asillustrated, a channel 60 may be accompanied by an icon 62 that lists auser's user name, screen name, or system name. In particularimplementations, as illustrated, the user name may take the form of aduostar name (**mike). The user may set up the channel (private channel)60, or the system 2 may set up the channel 60 when the user streamingthe content allows the viewing user access to view the streamed share.As illustrated, some shares from a user may be private shares, andvisible in the user's channel in the everybody-shares interface, but theicon 62 representing that private share may have the user's duostaraddress or other identifier (but no image), indicating that the user whois logged into the everybody-share's interface has not been givenpermission to see the private share. The user who wishes to see theprivate share may be able to contact the user by selecting the icon torequest permission to see the share through the system 2. Some publicshares that the user has not associated with a particular channel may beincluded in a Just-In channel and may be added to existing channel orinserted into a newly defined channel. The shares 64, 66 shown have therespective streaming users' subscriber names above the share icons.

As illustrated, additional scroll icons 68, 70 may be included withinthe channel container of a channel to permit the user to move aparticular share icon within its position within the channel. Also, asillustrated, one or more tap buttons 72 may be included adjacent to thechannel 60 which allow the system 2 (whether through the applicationserver 10 or web server 18) to store a record in the database 12 thatthe user would like to be notified when a new share for the channel 60is available. This notification may take place through the sending of anemail, a text message, a push notification in an app, or any othernotification to the user that a new share is available in that channel.As is illustrated in FIG. 4, since channels may be organized by contenttype rather than just by user, this means that a user may receivenotifications when live shares are available for a particular theme,content, geographic area, or other channel characteristic are availableto viewing, as well as when shares for a particular user of the systemare available.

FIG. 5 illustrates an implementation of a share-box interface 74 havinga plurality of shares 76, 78 and associated text 80, 82. On theleft-hand side of the screen, the duostar address for each user is shownin an icon next to the share icon. A scroll icon is shown to allow thesubscriber to scroll through shares within their share-box interface 74.The associated text 80 82 may come from the user who shared the sharewith the viewing user, and/or may be added by the viewing user when theshare arrives in the viewing user's share box interface 74. Shares inthe share-box interface 74 may be either live shares or saved shares.Shares in the share-box may also be public shares or private shares. Invarious implementations, the flexibility of the share-box interface maypermit a streaming user to send a live share to another receiving userand for the receiving user to send a corresponding live share back,enabling a video conference feature. Many other possibilities, includingvideo messaging, are possible. When a user deletes a particular savedshare from the system, as was previously described, it is permanentlydeleted, and also removed from being visible from the share-boxinterfaces associated with any other users who were given access to viewthe saved share. This behavior is enabled by use of the applicationserver 10 and the database 12, which deletes any association in thedatabase between the other saved users as well as deleting the savedvideo and audio data associated with that share.

FIG. 6 illustrates the share-box interface (an example of a viewinginterface) 74 of FIG. 5, showing the share associated with **mike in anenlarged size in response to being selected by the user. A user mayselect a share icon within the share-box to see the share in an enlargedsize. The size may be any suitable size and may take up substantiallythe entire screen in various implementations. In addition, thesubscriber may also be provided with options on clicking on the share asto how large they would like to view the shares in any of the interfacesas described herein. In the share-box interface 74 shown in FIG. 6, theshare icon is shown enlarged but not as a full screen display. The sharecan be viewed in this size, or may enlarge itself to be full screen ifdesired by the user.

FIG. 7 shows an implementation of an invisible shares interface 84(invisible computer interface) that has invisible shares channels 86, 88and an invisible shares inbox 90 each having icons 92, 94 correspondingwith invisible shares. The term “invisible share,” as used herein, isdefined as a share that is only accessible by users that have beenauthorized by the submitting user and is not discoverable through asearch using the search form 30, i.e., will never show up in any searchresults made using the search form 30 in any interface. The term“invisible computer interface” and “invisible shares interface” as usedherein, is defined as a computer interface that contains invisibleshares and/or invisible channels. As used herein, invisible computerinterfaces are visible to the users associated with various computingdevices used to generate them; the term “invisible” refers to theinability of anyone but that particular user to find any of the sharescontained in that interface using the search form 30 and searchfunctionality enabled by the database 12. The way the invisible sharesare kept invisible may be through several methods. For example, thedatabase 12 may simply not include any shares designated by users of thesystem 12 that contain a database record indicating the share isinvisible from appearing in any search results or may simply neverperform any searches or database queries that involve those shares,excluding them from the shares available for searching.

As illustrated, the invisible share interface includes channelscontaining invisible shares associated with the user and another one forinvisible shares received from other users. Because invisible shares arenot searchable, the only way for a viewing user of the system to view astreaming user's invisible share is for the streaming user to use ashare vault 96 included in the interface 84. In a particularimplementation, the streaming user inputs the viewing user's address(duostar) address into the share vault 96. The application server 2 thencreates a database entry in the database 12 indicating that the viewinguser is authorized to see all of the streaming user's invisible shares,and all of the available invisible shares for the streaming user,whether live or saved invisible shares then appear in the viewing user'sinvisible shares inbox 90. In other implementations, in order for theviewing user to see any shares (or a particular share), the streaminguser needs to select one or more of the invisible shares and then inputthe viewing user's address into the share vault 96. The viewing userthen inputs the streaming user's address into a receive vault 98 in aninvisible computer interface associated with the viewing user. At thatpoint, the application server 10 matches the database entries for theone or more invisible shares that indicated that these one or moreinvisible shares are to be made available to the viewing user, and theyappear in the viewing user's invisible shares inbox. A consequence ofboth approaches is that while the viewing user can see all of theinvisible shares for the streaming user, the streaming user cannotreciprocally see any of the invisible shares that the viewing user hasin their invisible share channels or inbox. This affirmative invitationprocess may assist the system 2 with protecting the privacy andconfidentiality of the information contained in the invisible shares.

In various implementations, the invisible shares interface 84 may beaccessible following a streaming user or viewing user logging into thesystem 2 using their standard user name and password. In otherimplementations, the invisible shares interface 84 may be accessibleonly after the user enters additional login information in a separatelogin section on any one of the interfaces disclosed herein, or afterselecting the option to login to the invisible shares interface 84through the options dropdown interface located on the interfacesdisclosed herein. The use of a separate login to access the invisibleshares interface 84 may allow users to prevent unauthorized orinadvertent access by others who obtain access to their system accountto the invisible shares they are streaming or have been given access to.Such a separate login may take the form and be similar to the structuresused in medical applications where separate logins are required toaccess sensitive or otherwise specifically controlled informationthrough the system. Such separate login capabilities to protect accessto the invisible share interface 84 may be particularly useful where thesystem 2 permits users to remain logged into the system 2 for a periodof time and does not require them to enter their login informationduring that time through the use of cookies and other user sessionpersistence methods and systems.

As illustrated, the use of invisible shares may permit the system 2 tobe utilized in situations where data privacy or confidentiality areimportant or valued by the users involved in the information exchange.For example, the invisible shares inbox 90 for the user illustratedcontains an entire channel dedicated to work-related shares, which couldinclude video inspection of factory equipment, confidential work-relatedmeetings, prototyping and/or research and development discussions, andother items for which the ability of the general population of users ofthe system being able to see even in icon private share form in searcheswould be undesirable. Other users may simply want to protect theirfamily privacy by ensuring that all family related shares are notvisible at any time while they are being sent, and will use theinvisible share interface 84 and the related methods to do so. A widevariety of possibilities are possible using the principles disclosedherein.

Referring to FIG. 9, an implementation of the public computer interface(another example of a viewing interface) 20 of FIG. 8 is illustratedshowing messaging 100 indicating that a particular public or privateshare associated with a particular user of the system has been sent tosomeone who has not yet established an account or is not currentlylogged into their account with the system 2. The messaging 100 includesthe duostar address of the user who sent the share, and, as the share isa public share in this case included in the Most Popular Shares channel,the icon associated with that share is shown selected and enlarged inFIG. 9. In communicating the sending of the share to someone notcurrently logged into the system 2 or who is not yet a user of thesystem, the application server 10 or web server 18 may send an email,text or any other suitable electronic communication to someone asdirected by the user, whereby the communication has a link to thewebsite created by the system 2. When clicking on or activating thelink, the computing device associated with the person receiving the linkgenerates the computer interface illustrated in FIG. 9.

FIG. 11 illustrates an implementation of a channel data setup interface102 associated with the system 2. As illustrated in FIG. 11, inputfields are displayed for the user creating the channel to provideinformation related to a channel. The subscriber may label the channeland provide a user identified icon, and may provide search terms for thechannel. In addition, a subscriber may designate a channel as public,private, or invisible. In some implementations, invisible channels arecreated only from the invisible computer interface 84. The user may alsoprovide a list of users that are authorized to have access to the sharesfrom this channel. A user may also provide a list of users or emailaddresses for sending out alerts when the selected channel is streaminga share.

When setting up a channel in the system, the user also creates one ormore channel characteristics, which, through interaction between theapplication server 10 and the video camera 4 and/or portable computingdevice 6, become included in any share associated with that particularchannel. A wide variety of channel characteristics may be included invarious implementations, including all the aspects of channels alreadydisclosed in this document as well as, by non-limiting example,geographical tags, automatic geographical search terms, contextualgeographical search terms, contextual event search terms, GPScoordinates, user identities, and any other information desired toassociate with the channel.

The term “geographical tags,” as used herein, is defined as a digitallocation identifier that is included in the live POV video data sent tothe system with a share, and may comprise global positioningcoordinates, location names, and the like.

The term “automatic geographical search terms,” as used herein, aresearch terms (channel characteristics) that the application server 10assigns to a share that are related to the geographical tags. Forexample, the application server 10 may assign to a user's uploaded sharetaken at a football stadium in Philadelphia, automatic geographicalsearch terms such as Pennsylvania, Philadelphia, and/or LincolnFinancial Field.

The term “contextual geographical search terms,” as used herein, isdefined as search terms (channel characteristics) that are related tothe location where the share was recorded, as determined by thegeographical tag. For example, a user may record a share of a footballgame from the stands in Lincoln Financial Field, and the applicationserver 10 may ascertain through web based searching various contextualgeographical search terms such as, football stadium, football game,professional football, NFL, Philadelphia Eagles, and the like. Theapplication server 10 may automatically assign to the share or promptthe user with audio prompts through the capshall to select contextualgeographical search terms related to the location.

The term “contextual event search terms,” as used herein, is defined assearch terms (channel characteristics) that are related to the locationand time a share was recorded, as determined by embedded thegeographical tag and time stamp. For example, a user may record a shareof a football game from the stands in Lincoln Financial Field of theEagles playing the New York Giants, and the application server 10 mayascertain through web based searching what type of event is taking placeat the location and time. The application server 10 may thenautomatically assign to the share or prompt the user using audio throughthe capshall to select contextual geographical search terms related tothe location. For example, contextual event search terms associated withthe example provided may include, Philadelphia Eagles, New York Giants,NFL, and the like.

Referring to FIG. 10, an implementation of a search interface 104displayed after the search form 30 has been used is illustrated. Asillustrated, the search was run for the user with the duostar address of**wayjay4, showing those public shares and private shares the searchinguser has access to. The interface 104 includes a search display, wherebyone or more icons representing shares or channels are displayed. Theuser may then select an icon to view a share or a may request access tothe channel, or subscribe to the channel. The search terms associatedwith a share may be input by the streaming user when setting up thechannel or when streaming the share as previously discussed.

Any number of search terms may be associated with a share or channel. Inone embodiment, a share may have a geographical tag that identifies thelocation where the share is being recorded as was previously discussed.A user searching for shares or channels by location may input ageographical area, and the application server 10 may return to the usershare or channel icons having the associated geographical coordinates orcoordinates within a programed distance. The programed distance may beany suitable distance and may be a function of the search term input bythe user. For example, a user may input Baltimore as a search term, andchannels or shares having a geographical coordinate within the greaterBaltimore area may be displayed to the user. Likewise, a user may inputthe inner harbor of Baltimore as a search term and channels or shareshaving a geographic coordinate within the inner harbor area may bedisplayed to the user.

During playback of various shares, particularly those where search termsand/or geographical tags (or share content-related tags, terms, orkeywords are associated with the share) targeted picture-in-pictureadvertising may be included in the field of view of the share on thecomputing device on which the viewing user is viewing the share. Thiscould take the form of a static or animated advertisement (or even videoadvertising) placed in a separate frame in a corner of the main frame orin a portion of the interface in which the video associated with theshare is playing. In some implementations, the ads are not live content,but are prerecorded messages that are inserted into each video frame oflive POV video by the system during streaming of each live video frameof POV video. In other implementations, the ads could be live contentgenerated by an advertiser for playback during a particular share orduring playback of shares sharing particular related content (such as,by non-limiting example, during a pledge drive to support content of thetype the share is associated with).

Referring to FIG. 12, a database diagram 106 is illustrated for aparticular implementation of a database 12 used in a system 2implementation. As illustrated, the database includes a variety oftables with primary keys that enable the system 2, using the applicationserver 10, video streaming server 8, and web server 18 to control,manage, set, and remove access to various shares to streaming andviewing users, as well as provide access by new users to the system 2.

Referring to FIG. 13, a flow diagram of an implementation of a method ofgenerating and transmitting live streaming POV video 108 is illustrated.As illustrated, the method 108 includes encoding live POV video datausing a POV video camera (step 109), which may be any POV video cameradevice disclosed in this document. The method 108 also includesstreaming the live POV data into a wireless telecommunication channel toa portable computing device using a first data transmission protocol(step 110) and streaming the live POV video data into a wirelesstelecommunication channel to a video streaming server using a seconddata transmission protocol (step 112). The method may also includerecording one or more channel characteristics included in the live POVvideo data in a database (step 114) and streaming the live POV videodata into a telecommunication channel to a computing device associatedwith a user using a third data transmission protocol (step 116). Themethod 108 also includes processing the live POV video data a generatinga computing interface using the one or more channel characteristics(step 118). The method 108 includes determining if the channel type isinvisible or public (step 120), and if the channel type is public, thenthe method includes generating a public computer interface and iconassociated with the live POV video (step 122). If the channel type isinvisible, then the method includes generating an invisible computerinterface and icon associated with the live POV video data (step 124).The method 108 also includes in response to selection of the iconassociated with the live POV video data, playing the live POV video in aviewing computer interface using the computing device (step 126).

In various method implementations, the method may also include cachingthe live POV video data on the application server 10 (or video streamingserver 8) to form a share and providing access to another user (viewinguser) of the system to the share on the application server 10 using thedatabase 12 and the application server 10 through generating an icon ina public computer interface, a private computer interface, or aninvisible computer interface corresponding with the type of share, ifthe share is a public share, private share, or invisible share,respectively. Any of the interface types and share types disclosedherein may be employed.

For shares that are private shares or invisible shares, the method mayinclude storing an entire quantity of live POV video data associatedwith the share on the application server 10 or video streaming server 8and providing access to a viewing users of the system to the share onthe application server 10 using the database 12 and the applicationserver 10 through generating an icon in the private computer interfaceor the invisible computer interface corresponding with the share. Invarious implementations of the system, the user can use the system 2 topost the saved shares (private or invisible) to various other websites,such as YouTube for longer-term archiving of the content.

In various implementations the method may further include, in additionto caching the live POV video or storing the entire quantity of live POVvideo data on the application server 10 or the video streaming server 8to create a share and then, in response to a selection of an addressassociated with another user (viewing user), creating an icon in a sharebox computer interface associated with other user using the database 12and the application server 10 along with a computer device associatedwith the viewing user. This same method implementation can also be usedto create a share icon in a channel that the viewing user has subscribedto.

Implementations of the method may further include, in addition tocaching the live POV video or storing the entire quantity of live POVvideo data on the application server 10 or video streaming server 8 tocreate an invisible share, in response to entry of an address (duostar,for example) associated with the receiving user (viewing user) in ashare vault associated with the user included in the invisible computerinterface and entry of an address associated with the user of the system(streaming user) included in an invisible computer interface on acomputing device associated with the receiving user, creating an icon inan invisible channel included in the invisible computer interfaceassociated with the receiving user using the database 12 and theapplication server 10. Implementations of the method where the receivinguser does not have to enter the streaming user's address into theirreceive vault may also be employed by various implementations of thesystem 2.

In various implementations of the system, the capshall may be operatedusing various methods. In particular implementations, the method 108 mayinclude activating the POV video camera to enter a channel selectionmode (which may be done by pressing a button on the capshall), audiblyspeaking one or more names of one or more channels associated with theuser from the POV video camera using an earpiece coupled to the POVvideo camera (included in the audio component), receiving a selection ofa channel (through the user pressing the button), audibly speaking thename associated with the selected channel (using the audio component),and activating the POV video camera to enter a recording mode. In therecording mode, the POV video camera begins to encode or otherwisestream live POV video data across the wireless telecommunication channelto the portable computing device 6.

When activating the capshall or POV video camera, the method may alsoinclude determining a location of the POV video camera using a GPSsignal received by the POV video camera and a location services system(such as those marketed under the tradename GOOGLE LOCATION SERVICES byGoogle, Inc.) access wirelessly by the POV video camera through theportable computing device associated with the user. The method may alsoinclude assigning one or more contextual geographical search terms tothe channel selected using the location and the POV video camera andincluding the location or the one or more contextual geographical searchterms in the one or more channel characteristics. The one or morechannel characteristics may be any disclosed in this document.

In places where the description above refers to particularimplementations of live streaming video sharing systems, relatedmethods, and implementing components, sub-components, methods andsub-methods, it should be readily apparent that a number ofmodifications may be made without departing from the spirit thereof andthat these implementations, implementing components, sub-components,methods and sub-methods may be applied to other live streaming videosharing systems and related methods.

What is claimed is:
 1. A method of generating and transmitting livestreaming point-of-view (POV) video, the method comprising: encodinglive POV video data using a POV video camera; streaming the live POVvideo data into a wireless telecommunication channel to a portablecomputing device operatively wirelessly coupled with the video camera,the live POV video data transmitted using a first data transmissionprotocol; streaming the live POV video data into a wirelesstelecommunication channel to a video streaming server operativelycoupled with the portable computing device through a wirelesstelecommunication channel, the live POV video data transmitted using asecond data transmission protocol; in response to receiving the live POVvideo data, recording one or more channel characteristics associatedwith the live POV video and included in the live POV video data in adatabase operatively coupled with the video streaming server and anapplication server, using one of the video streaming server and theapplication server; streaming the live POV video data into atelecommunication channel to a computing device associated with a userusing one of the video streaming server, the application server, and aweb server, the live POV video data transmitted using a third datatransmission protocol; and processing the live POV video data andgenerating a computer interface using the computing device and the oneor more channel characteristics, the computer interface comprising: ifthe one or more channel characteristics indicate the live POV video datais associated with a public channel, a public computer interfacecomprising the live POV video data, the public computer interfaceconfigured to allow a public user of the system to view the live POVvideo data; if the one or more channel characteristics indicate the livePOV video data is associated with an invisible channel associated withthe user, an invisible computer interface comprising the live POV videodata, the invisible computer interface configured to allow a user of thesystem having authorization to view the invisible channel to view thelive POV video data.
 2. The method of claim 1, further comprising:caching the live POV video data on the application server to form ashare; and providing access to another user of the system to the shareon the application server using the database and the application serverby generating an icon in one of the public computer interface, a privatecomputer interface, and the invisible computer interface correspondingwith the share if the share is a public share, private share, orinvisible share, respectively.
 3. A method of transmitting livestreaming video to a public channel and to an invisible channel, themethod comprising: receiving live video data using a streaming serverfrom a wireless telecommunication channel, the live video datatransmitted using a second data transmission protocol and a portablecomputing device, the portable computing device receiving the live videodata from a wireless telecommunication channel using a first datatransmission protocol from a video camera; in response to receiving thelive video data, recording one or more channel characteristicsassociated with the live video and included in the live video data in adatabase operatively coupled with the video streaming server and anapplication server, using one of the application server and the videostreaming server; providing access to the live video data using thedatabase and the one or more channel characteristics through atelecommunication channel using one of the video streaming server, theapplication server, and a web server, wherein one of the video streamingserver, the application server, and the web server are adapted to, inresponse to a request from a computing device associated with a user,stream the live video data using the telecommunication channel and athird data transmission protocol to the computing device, where thecomputing device is adapted to generate a computer interface using thecomputing device and the one or more channel characteristics where thecomputer interface comprises: if the one or more channel characteristicsindicate the live video data is associated with a public channel, apublic computer interface, wherein the public computer interfacecomprises the live video data and the public computer interface isconfigured to allow a public user of the system to view the live videodata; if the one or more channel characteristics indicate the live videodata is associated with an invisible channel associated with the user, aprivate computer interface, wherein the private computer interface isconfigured to allow a user of the system authorized to view theinvisible channel to view the live video data.
 4. The method of claim 3,further comprising: sharing the live video data with another user of thesystem by: one of caching the live video data and storing an entirequantity of live video data using one of the application server and thevideo streaming server to create a share; and in response to a selectionof an address associated with the other user, creating an icon in asharebox computer interface associated with the other user using thedatabase and the application server and a computing device associatedwith the other user.